Conversation
J3m5
force-pushed
the
pnpm
branch
2 times, most recently
from
7724ae2 to
fc38f13
Compare
Member
|
@dunglas can we merge this? I remember we had to use yarn because react-admin uses yarn but in this project it should be fine? |
J3m5
changed the title
soyuka
approved these changes
Jun 13, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Build 📦
Transition the package manager from Yarn to PNPM, updating the Readme, CI configuration and scripts accordingly.
Why migrate from Yarn 1 (1.22.22) to pnpm 10 (10.11.0) ?
node_modules– hard-link store saves ~60 % diskpnpm-lock.yaml+ declared-only imports, no “phantom” deps